Skip to content

fix: escape input before returning #4810

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 18 commits into from
Closed

fix: escape input before returning #4810

wants to merge 18 commits into from

Conversation

mohamedzeidan2021
Copy link
Contributor

Issue #, if available:

Description of changes:
Fixing the potential cross site scripting vulnerability by escaping the input using flasks escape function before returning the request data in the case that the request fails.

Testing done:
The code scanning vulnerability disappeared in my fork once the fix was implemented.

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

General

  • [x ] I have read the CONTRIBUTING doc
  • [x ] I certify that the changes I am introducing will be backward compatible, and I have discussed concerns about this, if any, with the Python SDK team
  • [ x] I used the commit message format described in CONTRIBUTING
  • I have passed the region in to all S3 and STS clients that I've initialized as part of this change.
  • I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

  • I have added tests that prove my fix is effective or that my feature works (if appropriate)
  • I have added unit and/or integration tests as appropriate to ensure backward compatibility of the changes
  • I have checked that my tests are not configured for a specific region or account (if appropriate)
  • I have used unique_name_from_base to create resource names in integ tests (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Delete .github/workflows/security-monitoring.yml
@mohamedzeidan2021 mohamedzeidan2021 requested a review from a team as a code owner July 29, 2024 19:19
@mohamedzeidan2021 mohamedzeidan2021 requested a review from ptkab July 29, 2024 19:19
@@ -106,4 +106,4 @@

return response
except Exception as e:
return f"Error during model invocation: {str(e)} for input: {request.get_data()}"
return f"Error during model invocation: {str(e)} for input: {escape(request.get_data())}"

Check warning

Code scanning / CodeQL

Information exposure through an exception

[Stack trace information](1) flows to this location and may be exposed to an external user.
config_value,
source_value,
config_value_log_copy,
source_value_log_copy,

Check failure

Code scanning / CodeQL

Clear-text logging of sensitive information

This expression logs [sensitive data (secret)](1) as clear text. This expression logs [sensitive data (secret)](2) as clear text. This expression logs [sensitive data (secret)](3) as clear text. This expression logs [sensitive data (secret)](4) as clear text.
config_value,
source_value,
config_value_log_copy,
source_value_log_copy,

Check failure

Code scanning / CodeQL

Clear-text logging of sensitive information

This expression logs [sensitive data (secret)](1) as clear text. This expression logs [sensitive data (secret)](2) as clear text. This expression logs [sensitive data (secret)](3) as clear text. This expression logs [sensitive data (secret)](4) as clear text.
@mohamedzeidan2021 mohamedzeidan2021 closed this by deleting the head repository Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants